fix(desktop): keep storyboards distinct from dashboards on shared code paths - #787
Draft
lauren-jacksonSFDC wants to merge 3 commits into
Draft
fix(desktop): keep storyboards distinct from dashboards on shared code paths#787lauren-jacksonSFDC wants to merge 3 commits into
lauren-jacksonSFDC wants to merge 3 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Work item: W-23854534 — bring storyboards to parity with worksheets/dashboards.
Decision
A story serializes as
<dashboard type='storyboard'>and already rides the dashboard machinery (apply, cache, validation, inventory). This closes the storyboard/dashboard consistency gaps that do not need the deferred whole-workbook read fallback. The rule the codebase now keeps: the dashboard metadata resolvers treat a<dashboard type='storyboard'>as not a dashboard, so a story never leaks into the dashboard surface.Changes
listDashboardRefs/resolveDashboardRef/extractDashboardXmlnow skip@_type='storyboard'. Before this, on an older Desktop build using the whole-workbook-document fallback,list-dashboardsreturned stories andget-dashboard-xmlcould hand back a story fragment as a dashboard.resolveCanonicalDashboardNametakes the loadkind, so a storyboard apply that trips the name / workbook-document gate is told aboutstoryboardName, notdashboard_name. The<dashboard>element tag and theread-cached-xml dashboard=selector stay literal — a story is a<dashboard>element and is sliced with that selector.get-storyboard-xmlaligned to its get-xml siblings.storyboardNameis now required, the deprecatedstoryboardalias param is dropped, and the description matchesget-dashboard-xml/get-worksheet-xml. Shrinks the dynamic-authoring tool surface by 51 bytes (byte-budget re-pinned inserver.desktop.test.ts).listStoryboards.test.ts; storyboard slice/splice cases in the cache tests; dashboard-resolver exclusion cases.Deferred (out of scope, by design)
list-storyboards/get-storyboard-xml— only helps Desktop builds that serve/v0/workbook/documentbut not the newer/storyboardsroutes (a narrow window). Consequence: with dashboards now excluding stories, a story on such an old build is simply not enumerable there (correct, not misclassified).list-storyboardsto the defaultDYNAMIC_AUTHORING_TOOL_PROFILE(discovery-only; editing a named story still works).Testing
npm run lintclean.npm run build:desktopsucceeds.🤖 Generated with Claude Code